-
Notifications
You must be signed in to change notification settings - Fork 259
RC: AWS PrivateLink #2150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
RC: AWS PrivateLink #2150
Conversation
weight: 90 | ||
--- | ||
|
||
[Amazon Web Services (AWS) PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-resources.html) allows you to securely connect your Amazon virtual private cloud(s) (VPCs) to Redis Cloud without using public IP addresses or traversing the public internet. PrivateLink provides private connectivity between VPCs, simplifying your network architecture and reducing exposure to security threats. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cmilesb Instead of saying that it securely connects between VPCs, I'd prefer to say here something along the lines of PrivateLink allows service providers (i.e. Redis) to securely expose specific services without exposing the entire service provider and consumer VPCs to each other (as is the case with VPC peering/TGW for example). AWS do this by having a representation of the service (resource) in the consumer VPC and the consumer uses that local representation as if the resource was in the consumer VPC. Indeed not needing to care about deployment CIDRs is another benefit as a result of that. Not sure how to phrase it clearly but that is the idea.
I wasn't able to get this to fully work, but here's what I have so far.